bitkeeper revision 1.1462 (428c884242SexXIVbHWO-OkTk2Q95w)
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Thu, 19 May 2005 12:36:18 +0000 (12:36 +0000)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Thu, 19 May 2005 12:36:18 +0000 (12:36 +0000)
commitc17b1a485fa7ed44d5f6e519d567f52ae7fc5200
treea107b10263115bb7e8144044cbf147bc29c07cb7
parent418babe999dbd4c5091efdb987fd5b1c47c8177a
bitkeeper revision 1.1462 (428c884242SexXIVbHWO-OkTk2Q95w)

Clean up, fix, and rationalise RAM mapping in Xen.

First, x86/64 must take care to map only registered RAM areas and not
adjacent I/O holes -- otherwise a cpu may cache I/O space and cause
coherency conflicts on the memory bus.

Second, map_pages() and the memguard mechanisms are no longer sub-arch
specific (moved to arch/x86/mm.c:map_pages_to_xen()).

Signed-off-by: Keir Fraser <keir@xensource.com>
xen/arch/x86/acpi/boot.c
xen/arch/x86/boot/x86_64.S
xen/arch/x86/domain.c
xen/arch/x86/domain_build.c
xen/arch/x86/mm.c
xen/arch/x86/setup.c
xen/arch/x86/x86_32/mm.c
xen/arch/x86/x86_64/mm.c
xen/include/asm-x86/mm.h
xen/include/asm-x86/page.h